K8s: warn against force delete #1864
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
dwdougherty
approved these changes
Jul 22, 2025
Collaborator
dwdougherty
left a comment
dwdougherty
left a comment
There was a problem hiding this comment.
Just a couple of comments. I'll go ahead and approve so you're not held up.
content/operate/kubernetes/re-clusters/delete-custom-resources.md
Outdated
Show resolved
Hide resolved
zcahana
reviewed
Jul 23, 2025
| {{< warning >}} | ||
| Use graceful deletion methods | ||
|
|
||
| When deleting Redis Enterprise resources or pods, try to avoid use `kubectl delete --force` or similar force deletion commands, as these can lead to: |
Contributor
There was a problem hiding this comment.
I'm wondering whether we should actually say that, because:
--forceflag doesn't have any effect on custom resources - it doesn't change the deletion behavior. In fact, I'm not aware of any k8s resource besides Pods that support non-graceful deletion. The k8s documentation vaguely say that "only a subset of resources support graceful deletion", but I believe this comes down to... pods only.- Regardless, users don't need to, and typically shouldn't, delete operator-managed resources on their own. They should only delete custom resources that they've created (REC, REDB, ...), and the operator should take care of deleting related/managed resources that it created. Particularly, users shouldn't be deleting REC pods directly.. this typically leads to problems.
Co-authored-by: David Dougherty <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
DOC-2276